Estimation using image analysis

ABSTRACT

Techniques are described for performing estimations based on image analysis. In some implementations, one or more images may be received of at least portion(s) of a physical object, such as a vehicle. The image(s) may show damage that has occurred to the portion(s) of the physical object, such as damage caused by an accident. The image(s) may be transmitted to an estimation engine that performs pre-processing operation(s) on the image(s), such as operation(s) to excerpt one or more portion(s) of the image(s) for subsequent analysis. The image(s), and/or the pre-processed image(s), may be provided to an image analysis service, which may analyze the image(s) and return component state information that describes a state (e.g., damage extent) of the portion(s) of the physical object shown in the image(s). Based on the component state information, the estimation engine may determine a cost estimate to repair and/or replace damaged component(s).

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation application of and claims priorityunder 35 U.S.C. § 120 to U.S. application Ser. No. 16/673,492, filedNov. 4, 2019, which is a continuation application of and claims priorityto U.S. application Ser. No. 15/870,509, filed on Jan. 12, 2018, whichis related to, and claims priority to, U.S. Provisional PatentApplication Ser. No. 62/445,971, titled “Estimation Using ImageAnalysis,” which was filed on Jan. 13, 2017, the entirety of each ofwhich are incorporated by reference into the present disclosure.

BACKGROUND

Following an accident that causes damage to an insured object, such as avehicle, the damaged object is typically examined to determine theextent of the damage and/or the cost to repair the damage.Traditionally, such an examination involves an inspection of the damagedobject by one or more individuals, which may be time-consuming andexpensive. Moreover, the individuals performing the inspection may havevarying degrees of expertise and/or diligence. Accordingly, the repaircost estimates determined through the traditional process may beinaccurate.

SUMMARY

Implementations of the present disclosure are generally directed to adetermining cost estimates for physical objects. More particularly,implementations of the present disclosure are directed to determiningrepair cost estimates for a physical object, based on results ofanalyzing one or more images of the damaged object.

In general, innovative aspects of the subject matter described in thisspecification can be embodied in methods that include operations of:receiving at least one image of a physical object, the at least oneimage generated using an image capture device; transmitting the at leastone image to a computer-implemented image analysis service andreceiving, in response, component state information indicating a stateof at least one component of the physical object, the state determinedbased on an analysis of the at least one image by thecomputer-implemented image analysis service; based at least partly onthe component state information, determining cost estimate informationthat describes a cost corresponding to the state of the at least onecomponent of the physical object; and transmitting the cost estimateinformation for presentation on a computing device.

These and other implementations can each optionally include one or moreof the following innovative features: the physical object is a vehicle;transmitting the cost estimate information includes communicating thecost estimate information to a service provider for repairing thephysical object; the operations further include performing at least onepre-processing operation prior to providing the at least one image tothe image analysis service; the at least one pre-processing operationincludes one or more of fraud checking, image sufficiency checking, orimage adjustment; image sufficiency checking includes checking that theat least one image is from at least a minimum number of differentviewpoints to enable the image analysis service to determine thecomponent state information; image sufficiency checking includeschecking that the at least one image has a minimum contrast level; thecomponent state information further includes a confidence level for thestate determined for the at least one component; the operations furtherinclude receiving information indicating prior damage to one or morecomponents of the physical object; the cost estimate information isfurther based on the prior damage; and/or the cost is to repair orreplace the at least one component of the physical object.

Other implementations of any of the above aspects include correspondingsystems, apparatus, and computer programs that are configured to performthe actions of the methods, encoded on computer storage devices. Thepresent disclosure also provides a computer-readable storage mediumcoupled to one or more processors and having instructions stored thereonwhich, when executed by the one or more processors, cause the one ormore processors to perform operations in accordance with implementationsof the methods provided herein. The present disclosure further providesa system for implementing the methods provided herein. The systemincludes one or more processors, and a computer-readable storage mediumcoupled to the one or more processors having instructions stored thereonwhich, when executed by the one or more processors, cause the one ormore processors to perform operations in accordance with implementationsof the methods provided herein.

Implementations of the present disclosure provide one or more of thefollowing technical advantages and improvements over traditionalsystems. Through cost estimation based on image analysis,implementations provide cost estimates that are more accurate,consistent, and objectively determined than estimates developed intraditional settings which may vary based on the varying expertise anddiligence of the estimator, and which may depend on the subjectiveopinions of the estimator. Because implementations provide more accurateand reliable cost estimates compared to traditional methods,implementations also consume less processing power, network capacity,storage space, active memory, and/or other computing resources comparedto systems that support traditional estimation techniques, given thatsuch traditional systems may be required to repeat processing of anestimation operation to recover from inaccurate estimates. Moreover,implementations enable cost estimation to be performed in real time inresponse to receiving image(s) of a damaged object, reducing the amountof time needed to respond to the damage-causing incident (e.g.,accident). Such real-time estimation also enables other follow-upactions to be performed in real time with respect to the analysis. Forexample, a determination may be made in real time whether to send avehicle to a repair shop or a salvage yard based on the real time imageanalysis and cost estimation following an accident, thus avoiding thecost of storing a vehicle until a traditional manual inspection can beperformed. Moreover, implementations reduce storage costs and/or repairtimes in some instances. For example, the parts for the vehicle can beordered at the time of the estimate so that parts that need shipping,customization, and/or manufacturing can have a shorter lead time, thusreducing the storage costs and the time to repair.

It is appreciated that aspects and features in accordance with thepresent disclosure can include any combination of the aspects andfeatures described herein. That is, aspects and features in accordancewith the present disclosure are not limited to the combinations ofaspects and features specifically described herein, but also include anycombination of the aspects and features provided.

The details of one or more implementations of the present disclosure areset forth in the accompanying drawings and the description below. Otherfeatures and advantages of the present disclosure will be apparent fromthe description and drawings, and from the claims.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 depicts an example system for estimation based on image analysis,according to implementations of the present disclosure.

FIG. 2 depicts an example schematic of component state informationemployed in estimation, according to implementations of the presentdisclosure.

FIG. 3 depicts a flow diagram of an example process for an estimationbased on image analysis, according to implementations of the presentdisclosure.

FIG. 4 depicts an example user interface, according to implementationsof the present disclosure.

FIG. 5 depicts an example computing system, according to implementationsof the present disclosure.

DETAILED DESCRIPTION

Implementations of the present disclosure are directed to systems,devices, methods, and computer-readable media for performing estimationsbased on image analysis. In some implementations, one or more images maybe received. The image(s) may be captured by image capture component(s)(e.g., a camera) of a user device, such as the user's smartphone, tabletcomputer, wearable computer, or other suitable computing device. Theimage(s) may be of one or more portions of a physical object, such as avehicle, building, or other tangible object. In some instances, theimage(s) may show damage that has occurred to the portion(s) of thephysical object. For example, a user may use their smartphone to captureone or more image(s) of their automobile after an accident, and theimage(s) may show dents, crumpling, broken windows, and/or other typesof damage caused by the accident.

The image(s) may be communicated to an estimation engine executing on atleast one server computing device. In some implementations, theestimation engine may perform one or more pre-processing operations onthe image(s), such as operation(s) to excerpt one or more portion(s) ofthe image(s) for subsequent analysis. The image(s), or the pre-processedimage(s), may be provided to an image analysis service. The imageanalysis service may analyze the image(s) and return component stateinformation that describes a state (e.g., damage extent) of one or morecomponents of the physical object shown in the image(s). Based on thecomponent state information, the estimation engine may determine a costestimate, such as an estimate of the cost to repair at least some of thedamage shown in the image(s) and/or replace one or more damagedcomponents.

Through the use of image analysis to determine repair and/or replacementcosts, implementations provide a more accurate estimate than that whichmay be determined through traditional inspection of the damaged object.Moreover, implementations provide for an estimation process which may beperformed more quickly and more efficiently compared to a traditionalinspection, given that the image-based analysis of the damage may beperformed through execution of the estimation engine without the needfor a manual inspection to determine damage extent and cost of repair orreplacement. In some instances, the image-based cost estimation processmay be performed in real time relative to receiving the image(s).

In some implementations, the cost estimates are based at least partly onthe time to complete an estimate, appraiser time, testing equipment,and/or material costs. Part of the learning performed by the algorithmis due to the availability of a large number (e.g., approximately 1.5million per year, over more than 10 years) estimates with detailed partslists in one or more databases. Such estimates can also include images,enabling the algorithm analyze the images and learn what parts need tobe replaced in instances that exhibit similar damage. In this way, thealgorithm can learn how to generate the estimate, and/or learn how togenerate a more accurate estimate, by examining millions of vehicles anddetermining the extent and type of damage.

FIG. 1 depicts an example system for estimation based on image analysis,according to implementations of the present disclosure. As shown in theexample of FIG. 1 , a user 102 may employ a user device 104 to captureone or more images 112 of a damaged object 106. The user device 104 maybe a portable (e.g., mobile) computing device such as a smartphone,tablet computer, wearable computer, and so forth. The user device 104may be any other suitable type of computing device. The user device 104may include one or more image capture components 108. The image capturecomponent(s) 108 may include hardware components of the user device 104,such as a camera configured to capture still image(s) and/or video of ascene. The image capture component(s) 108 may also include softwarecomponents configured to control the camera(s) and/or process the imageand/or video data captured by the camera(s). In some instances, theimage capture component(s) 108 may be external to the user device 104,and may communicate with the user device 104 over one or more wired orwireless networks. For example, an external camera may connect with theuser device 104 over a wireless (e.g., Bluetooth™) connection, andprocesses executing on the user device 104 may employ the externalcamera to capture image(s) and/or video data. The user device 104 mayalso be described as an image capture device.

Although FIG. 1 depicts the object 106 as a vehicle (e.g., anautomobile), implementations provide for image-based cost estimation forother appropriate types of physical objects as well. For example, thephysical object 106 may be a house, apartment, condominium, office,industrial facility, hotel room, and/or other type of structure orroom(s) of a structure. The physical object 106 may be another type ofvehicle such as a motorcycle, aircraft, watercraft, bicycle, and soforth. The physical object 106 may be a piece of furniture, work of art,tree or other type of plant, and so forth.

The user device 104 may execute an application 110, which may also bedescribed as a user application or app. The application 110 may receiveone or more images 112 captured by the image capture component(s) 108.In some instances, the image capture component(s) 108 may generate theimage(s) 112 and store the image(s) 112 in memory on the user device 104or elsewhere, and the application 110 may retrieve the image(s) 112 fromthe memory. In some instances, the application 110 may receive theimage(s) 112 (e.g., directly) from the image capture component(s) 108without intermediary storage of the image(s) 112. The image(s) 112 mayinclude any appropriate number of still image(s), and/or video data ofany suitable size.

The application 110 may communicate the image(s) 112, over one or morenetworks, to one or more server devices 114. The server device(s) 114may include any suitable number and type of computing device(s). In someinstances, the server device(s) 114 include server(s) for distributedcomputing and/or cloud computing. The server device(s) 114 may executean estimation engine 116. The estimation engine 116 may receive theimage(s) 112, and communicate the image(s) 112 to an image analysisservice 118. The image analysis service 118 may be remote from theserver device(s) 114 and may be provided by one or more other computingdevice(s). In such instances, the estimation engine 116 may communicatewith the image analysis service 118 over one or more networks. In someinstances, the image analysis service 118 may execute on the same serverdevice(s) 114 as the estimation engine 116.

The image analysis service 118 may analyze the image(s) 112 and generatecomponent state information 120 that describes, for one or morecomponents of the object 106, an extent of damage to the component. Thecomponent state information 120 is described further with reference toFIG. 2 . The component state information 120 may be received by theestimation engine 116 and employed to determine cost estimateinformation 122. The cost estimate information 112 may be communicatedand/or otherwise provided to one or more computing devices forpresentation through a user interface (UI). The cost estimateinformation 122 may include a cost to repair and/or replace each of oneor more damaged components of the object 106, and/or the cost to repairthe object 106 as a whole.

In some implementations, the image analysis service 118 may employmachine learning (ML) techniques to analyze the image(s) 112. Such MLtechniques may include, but are not limited to, techniques that employdeep learning neural networks for pattern recognition within theimage(s) 112, or to perform other types of analysis. Moreover, in someimplementations the estimation engine 116 may also employ ML techniquesto generate the cost estimate information 122 based at least partly onthe component state information 120. ML techniques may includesupervised and/or unsupervised ML techniques.

In some implementations, the application 110 may present the image(s)112 of the object 106 and prompt the user 102 to provide moreinformation regarding the image(s) 112 and/or the situation. Forexample, the user 102 may be prompted to input a cause or othercircumstances of the accident, and such information may be provided tothe estimation engine 116 with the image(s) 112. The estimation engine116 may take such information into account when determining the costestimate information 122. For example, the cost estimate information 122may include insurance-related information such as a covered cost, claimamount to be paid, claim amount to not be paid, deductible to be paid bythe user 102, and so forth, and these amounts may be determined based atleast partly on the cause and/or other circumstances of the accident. Ininstances where implementations are employed within an insurancecontext, the estimation engine 116 may also perform other operationssuch as confirming that the user 102 has a current, active, and validinsurance policy that covers the object 106.

In some implementations, the application 110 may present the image(s)112 and prompt the user 102 to note those areas of damage which may havebeen present prior to the accident, such as pre-existing dents orscratches on a vehicle. The application 110 may enable the user 102 tonote the previous areas of damage by circling, or otherwise indicating,those portions of the image(s) 112 that show previous damage. In suchinstances, the previous damage information may be communicated to theestimation engine 116, and the estimation engine 116 may take theprevious damage into account when generating the cost estimateinformation 112. For example, the cost estimate information 122 mayinclude a cost of repairing and/or replacing component(s) that weredamaged in the current accident, but may omit the cost of repairingand/or replacing those component(s) that were already damaged prior tothe accident. In some implementations, the estimation engine 116 mayaccess previously received image(s) of the object 106 that are stored onthe server device(s) 114 or elsewhere. The estimation engine 116 maycompare the previously received image(s) with the current image(s) 112of the object 106 to determine whether any of the damage shown in theimage(s) 112 was already present prior to the accident. In someimplementations, the estimation engine 116 may indicate previous damageto the image analysis service 118, and image analysis service 118 maygenerate the component state information 120 to not reflect the previousdamage.

In some implementations, the cost estimate information 122 may bedetermined in real time relative to receiving the image(s) 112, and/orshortly following the accident that caused the damage to the object 106.As used herein, a real time action is an action that is performedimmediately following a triggering event, accounting for the time neededto communicate and/or process information. A real time action may beperformed synchronously with respect to the triggering event, and/orwithin a same execution path as the detection of the triggering event.For example, in response to a triggering event of receiving the image(s)112, the estimation engine 116 may: pre-process the image(s) 112, sendthe image(s) 112 to the image analysis service 118, receive thecomponent state information 120 from the image analysis service 118(e.g., synchronously with sending the image(s) 112 to the service 118),determine the cost estimate information 122, and/or provide the costestimate information 122 for presentation in the UI of one or morecomputing device(s) such as the user device 104 and/or other device(s).Such real time processing may also enable other action(s) to beperformed in real time. For example, determining the cost estimationinformation 122 in real time shortly following an accident may enable adetermination to be made, in real time, whether a damaged vehicle is tobe sent to a salvage yard (e.g., if the vehicle is a total loss) or to arepair shop. The cost estimate information 122 and/or other (e.g.,insurance-related) information may also be communicated to the repairshop in real time, to expedite repair of the object 106.

In some implementations, the estimation engine 116 may perform one ormore pre-processing operations on the image(s) 112 prior to sending theimage(s) and/or pre-processed image(s) to the image analysis service118. Pre-processing may include one or more of the following: fraudchecking, image sufficiency checking, and/or image adjustment.

With respect to fraud checking, the estimation engine 116 may performcertain operation(s) that attempt to detect and prevent possiblyfraudulent insurance claims. For example, the information received fromthe user device 104 may be checked for consistency with otherinformation that describes the user 102, user device 104, and/or object106. In some implementations, a vehicle identification number (VIN) ofthe object 106 may be retrieved from the image(s) 112, and compared toinformation describing one or more insured vehicles of the user 102, toconfirm that the vehicle is covered by a valid policy of the user 102.Make, model, year, color, and/or other descriptive information regardingthe vehicle may also be retrieved from the image(s) 112 and compared toinformation describing the insured vehicles of the user 102, to confirmthe vehicle is covered. Inconsistencies may indicate possible fraud.

In some instances, fraud checking may also be performed based ongeographic location information that is embedded in the image metadataand/or otherwise received from the user device 104. Such information maybe compared to address information for the user 102 to determine whetherthe accident occurred in an area typically frequented by the user 102.If the location indicated in the image metadata and/or the currentlocation of the user device 104 differs from the typical location of theuser 102, the estimation engine may flag the image(s) 112 as possiblyfraudulent.

Fraud checking may include verifying the user's identity. The identityof the user 102 may be verified, and/or the user may be authenticated,through use of user-provided credentials (e.g., username, password, PIN,etc.), biometric data (e.g., fingerprint verification, facialrecognition, voice print identification, etc.), and/or other techniques.

Fraud checking may also include verifying other information provided bythe user 102 through the application 110. In instances where the user102 provides information describing the cause of the accident, suchinformation may be checked against other sources of information forconsistency. For example, if the user indicates that a vehicle wasdamaged during a flood, the estimation engine 116 may access weatherand/or disaster relief information to verify that flooding is occurringin the user's vicinity. As another example, if the user indicates thatthe vehicle was damaged in an accident with another vehicle, theestimation engine 116 may access traffic camera data, police records,and/or other sources of information to verify that an accident occurred.

Pre-processing may include image sufficiency checking to determinewhether the received image(s) 112 include sufficient information forfurther analysis. For example, the estimation engine 116 may analyze thereceived image(s) 112 to determine whether there is enough contrast inthe image(s) 112 to identify the object 106 and/or discern the damage tothe object 106. The image(s) 112 may also be checked to verify thatthere are enough image(s) 112, captured from a sufficient number ofdifferent viewpoints, locations, and/or angles, to be useable forfurther analysis. If the image(s) 112 are insufficient with respect tocontrast, number of angles, and/or other criteria, the estimation engine116 may instruct the application 110 to present a message describing theinsufficiency of the image(s) 112 to prompt the user 102 to provide moreand/or different image(s) 112.

In some implementations, the application 110 may provide guidance to theuser regarding the image(s) 112 to be captured. For example, theapplication 110 may provide guidance regarding the angles at whichimage(s) are to be taken, the size of the image(s), and so forth. Theapplication 110 and/or the estimation engine 116 may determine whetherimage(s) 112 are sufficient for the analysis. The application 110, basedon its own analysis of the image(s) and/or on instructions from theestimation engine 116, may request that the user use the device tocapture another set of images to reduce glare, eliminate obstructions,obtain better focus, and/or otherwise improve on the initial image(s) togenerate image(s) that are suitable for analysis. In someimplementations, the application 110 may provide a visualization thatincludes a wireframe or other indicator showing where, in the frame, thedamage is to be located, to help the user take image(s) that aresuitable for analysis.

In some implementations, pre-processing may include image adjustment,such as adjusting the size, format, color palette, resolution, and/orother characteristics of the image(s) 112 prior to sending them to theimage analysis service 118. Image adjustment may also includesub-windowing and/or otherwise extracting portion(s) of the image(s) 112for further processing. For example, the image(s) 112 may be croppedand/or excerpted to focus on those portion(s) of the image(s) 112 thatshow the object 106 and/or the damaged portion(s) of the object 106.

In some implementations, estimation engine 116 may access other inputdata 124 which is used to determine the cost estimate information 122.For example, the other input data 124 may include information describingthe cost of labor and/or parts in various regions, which may be used todetermine the cost estimate information 122 based on the component stateinformation 120. The cost estimate information 122 may also be based onother input data 124 that describes a history of similar damage to other(e.g., similar) vehicles, and the cost of previously repairing suchdamage. In some instances, such historical information may be employedto adjust an initial cost estimate based on how prior estimates comparedto the cost of actual repair or replacement in previous instances. Insome implementations, the estimation engine 116 may employ a ML-basedmodel that is trained using training data that includes prior costestimates and actual cost information. Accordingly, the estimationengine 116 may be trained over time to develop a more accurate costestimate based on the previous divergence between estimates and actualcost.

Other input data 124 may also include one or more of the following:weather data, traffic data (e.g., traffic camera and/or stoplight cameraimages), information from other vehicles, information from other sensorsthat are fixed or mobile (e.g., drone-mounted), police and/or accidentreports, social media data, auto shop and/or other service information,data (e.g., real time data) describing location of tow trucks, and soforth. In some implementations, the other input data 124 may includedata from in-vehicle computing devices and/or sensors, such as onboardautomotive computers, telematics devices, and/or sensors to determinespeed, orientation, location, acceleration/deceleration, braking, fuelconsumption, temperature, air pressure, ambient sound, and/or otherdata.

In some implementations, the other input data 124 includes telematicsdata that is collected and/or generated by an on-board system on thevehicle, and/or other sensor device(s) that are incorporated into thevehicle. Such telematics data can be used in conjunction with theimage(s) and/or component state information 120 to provide greaterconfidence that the damage analysis and/or cost estimate is accurate. Insome instances, the telematics data may include acceleration information(e.g., collected by accelerometer sensor devices and/or other suitablesensors) that indicates an acceleration or deceleration of the vehiclealong one or more references axes (e.g., in three dimensions), at one ormore times. Such acceleration data can also describe a force vector,indicating forces that are applied to the vehicle in one or moredirections, at one or more times. The telematics data may also includesensor data generated by fault sensors in various vehicle components,which indicate damage to and/or failure of the component(s). Thetelematics data can be used in conjunction with the image data and/orcomponent state information to develop greater confidence that thedamage inferred based on the image(s) is actually present on thevehicle. For example, apparent damage to a right panel on the vehiclemay be correlated with telematics data indicating a force applied to theright side of the vehicle (e.g., an impact from another vehicle), todevelop higher confidence that the damage to the right panel isaccurately identified and cost-estimated. Telematics data can also beemployed to develop a more accurate estimate of the degree of damage toa vehicle component. For example, the telematics data can be used todistinguish whether damage caused to a bumper of the vehicle was causedby a glancing blow (e.g., less force) versus a full-on collision (e.g.,greater force).

In some implementations, the estimation engine 116 may identify damagedcomponents with varying degrees of specificity. For example, damage maybe identified to a larger part (e.g., the right side of the vehicle)and/or to sub-components (e.g., a right front panel, right passengerdoor, etc.). Damage may also be inferred to non-visible parts of thevehicle, based on the damage that is visible in the image(s). Forexample, based on particular damage to a bumper, which is visible in theimage(s), an inference can be made that some underlying structure belowthe bumper has also been damaged, based on a degree of damage shown tothe bumper. Such inferences may be based on vehicle structuralinformation that describes the underlying structure, materialcomposition, design, and/or other aspects of the particular vehiclebeing imaged and analyzed. Vehicle structural information may beaccessed from a database on the server device(s) 114 and/or through aremote service.

In the example of FIG. 1 , the image(s) 112 are uploaded to theestimation engine 116 from the user device 104. In some implementations,the image(s) 112 are uploaded to some other service, which thencommunicates the image(s) to the estimation engine 116 directory and/orvia one or more intermediary services, interfaces, and/or other softwaremodules on one or more computing device(s). In some implementations, theimage(s) 112 may be communicated from the user device 104 to the imageanalysis service 118, instead of passing through the estimation engine116 as an intermediary.

FIG. 2 depicts an example schematic of component state informationemployed in estimation, according to implementations of the presentdisclosure. As shown in the example of FIG. 2 , the component stateinformation 120 may include any appropriate number of records that eachdescribe, for a particular object 106, a component of the object 106. Arecord may include a component identifier (ID) 202 that identifies thecomponent. The component ID 202 may be a name, description, ID number,and/or other type of ID. A record may describe the state 204 of theobject 106, determined through analysis of the image(s) 112. In someinstances, the state 204 may provide a measure of the amount of damageto the component. The state 204 may be a percentage damage, for examplefrom a minimum value (e.g., 0) to a maximum value (e.g., 1 or 100) wherethe maximum indicates total damage and the minimum value indicates nodamage. The state 204 may also be descriptive, such as “dent with 2 cmdiameter.” In some implementations, a record also includes a confidencelevel 206 indicating a degree of confidence in the state 204information. For example, the image analysis service 118 may determinewith 0.50 confidence level (e.g., from 0 to 1) that a particularcomponent is 75% damaged, and may determine with 0.75 confidence levelthat another component is 90% damaged, and so forth. Accordingly, thestate 204 and the confidence level 206 may be independently determinedby the image analysis service 118. The component state information 120may be described as a set of name-value pairs, with component ID 202being the name, and the state 204 being the value, in which eachname-value pair may include a confidence level 206 indicating adetermined accuracy of the state estimate.

Implementations support varying degrees of granularity for identifyingcomponents of the object 106. For example, a vehicle may includecomponents passenger-side front door, driver-side rear door, and soforth, and/or more granular components such as passenger-side front doorwindow, passenger-side front door handle, passenger-side front doorpanel, passenger-side front door window mechanism, and so forth. In someimplementations, the component state information 120 may include recordsfor components with different specificity. For example, the componentstate information 120 may include a record for the passenger-side frontdoor as a whole as well as record(s) for sub-components of thatcomponent, such as for the window, panel, and/or other sub-components ofthe passenger-side front door. In some implementations, the componentstate information 120 may include a record describing the state 204 ofthe object 106 as a whole (e.g., the highest-level component of theobject). For example, a state 204 of 95% damage for a whole vehicle maybe used to determine that the vehicle is a total loss, such that it maybe more cost-effective to replace the vehicle instead of repair it.

In some implementations, the component state information 120 includesinformation to be used in determining whether an object 106 is a totalloss or not. The component state information 120 may also include aprobability that the object 106 is a total loss, the proportion of theobject 106 (e.g., weightage) that is damaged, and/or an overallcondition of the object 106.

In some implementations, the state 204 may be a binary indication ofwhether the corresponding component is damaged (e.g., 0 or 1, yes or no,etc.). Table 1, below, shows example component state information 120listing a state 204 (e.g., labeled “ATR_VAL_TXT”) for each of aplurality of components identified by component ID 202 (e.g., labeled“ATR_NM”).

TABLE 1 ATR_ ATR_GRP_ ATR_ VAL_ DC ATR_TYP_DC NM TXT DamagevehicleCondition bedDamageInd N Damage vehicleCondition damageInd YDamage vehicleCondition fluidLeakageInd U Damage vehicleConditionfrontBumperDamageInd N Damage vehicleCondition hoodDamageInd N DamagevehicleCondition leftFrontCornerDamageInd N Damage vehicleConditionleftFrontSideDamageInd N Damage vehicleCondition leftRearCornerDamageIndN Damage vehicleCondition leftRearSideDamageInd N DamagevehicleCondition leftSideDamageInd N Damage vehicleConditionmoderateFrontImpactIndicator N Damage vehicleConditionrearBumperDamageInd N Damage vehicleCondition rearCargoDoorDamageInd NDamage vehicleCondition rearWindowDamageInd N Damage vehicleConditionrightFrontCornerDamageInd Y Damage vehicleConditionrightFrontSideDamageInd Y Damage vehicleConditionrightRearCornerDamageInd N Damage vehicleConditionrightRearSideDamageInd Y Damage vehicleCondition rightSideDamageInd YDamage vehicleCondition roofDamageInd N Damage vehicleConditionsideDamageInd Y Damage vehicleCondition typeOfDamage BodyOnly DamagevehicleCondition vehicleDrivableIndicator N Damage vehicleConditionwheelsOrTiresDamageInd Y Damage vehicleCondition windShieldDamageInd N

FIG. 3 depicts a flow diagram of an example process for estimation basedon image analysis, according to implementations of the presentdisclosure. Operations of the process may be performed by one or more ofthe estimation engine 116, the application 110, the image analysisservice 118, and/or other software module(s) executing on the serverdevice(s) 114, the user device 104, or elsewhere.

The image(s) 112 of the object 106 may be received (302). In someimplementations, the image(s) 112 may be pre-processed (304) asdescribed above. The image(s) 112, and/or pre-processed image(s) 112,may be provided (306) to the image analysis service 118. The componentstate information 120 may be received (308) from the image analysisservice 118. As described above, the component state information 120 maybe generated based on the service's analysis of the image(s) 112. Basedat least partly on the component state information 120, the costestimate information 122 may be determined (310). In some instances, thedetermination of the component state information 120 may be furtherbased on the other input data 124, as described above. The cost estimateinformation 122 may be communicated or otherwise provided (312) forpresentation through a UI on one or more computing devices. In someinstances, the cost estimate information 122 may also be stored inmemory for subsequent access. In some instances, providing the costestimate information 122 may include communicating the cost estimateinformation 122 to a service provider, such as an automotive repairshop, garage, body shop, or other service that is to repair (or replace)the object 106 and/or component(s) of the object 106.

FIG. 4 depicts an example UI 402, according to implementations of thepresent disclosure. The UI 402 may be presented by the application 110,and may enable the user 102 to specify information to be sent to theestimation engine 116 to be used for determining the cost estimateinformation 122.

As shown in the example, the UI 402 may present an element 404 that isan image of the vehicle or other object 106. The element 404 may beclickable by the user 102 to select various components of the object106. For each selected component, the UI 402 may present an element 408that enables the user 102 to specify whether there is any known damage(e.g., previous and/or current damage) to the selected component. Foreach damaged component, the UI 402 may prompt the user 102 to captureone or more images 112 of the component for further analysis and costestimation. The UI 402 may provide an element 406 to enable the user 102to select the first point of impact and/or other information describingthe accident or other damage-causing incident. The UI 402 may alsoprovide an element 410 that lists the damaged areas of the object 106that have been indicated by the user 102. After the information has beenprovided, the user 102 may click a submit button 412 to cause theimage(s) 112 and/or other provided information to be sent to theestimation engine 116. A clear button 414 may be clicked to clear and/orcancel the entered information.

FIG. 5 depicts an example computing system, according to implementationsof the present disclosure. The system 500 may be used for any of theoperations described with respect to the various implementationsdiscussed herein. For example, the system 500 may be included, at leastin part, in one or more of the user device 104, the server device(s)114, and/or other computing device(s) or system(s) described herein. Thesystem 500 may include one or more processors 510, a memory 520, one ormore storage devices 530, and one or more input/output (I/O) devices 550controllable via one or more I/O interfaces 540. The various components510, 520, 530, 540, or 550 may be interconnected via at least one systembus 560, which may enable the transfer of data between the variousmodules and components of the system 500.

The processor(s) 510 may be configured to process instructions forexecution within the system 500. The processor(s) 510 may includesingle-threaded processor(s), multi-threaded processor(s), or both. Theprocessor(s) 510 may be configured to process instructions stored in thememory 520 or on the storage device(s) 530. For example, theprocessor(s) 510 may execute instructions for the various softwaremodule(s) described herein. The processor(s) 510 may includehardware-based processor(s) each including one or more cores. Theprocessor(s) 510 may include general purpose processor(s), specialpurpose processor(s), or both.

The memory 520 may store information within the system 500. In someimplementations, the memory 520 includes one or more computer-readablemedia. The memory 520 may include any number of volatile memory units,any number of non-volatile memory units, or both volatile andnon-volatile memory units. The memory 520 may include read-only memory,random access memory, or both. In some examples, the memory 520 may beemployed as active or physical memory by one or more executing softwaremodules.

The storage device(s) 530 may be configured to provide (e.g.,persistent) mass storage for the system 500. In some implementations,the storage device(s) 530 may include one or more computer-readablemedia. For example, the storage device(s) 530 may include a floppy diskdevice, a hard disk device, an optical disk device, or a tape device.The storage device(s) 530 may include read-only memory, random accessmemory, or both. The storage device(s) 530 may include one or more of aninternal hard drive, an external hard drive, or a removable drive.

One or both of the memory 520 or the storage device(s) 530 may includeone or more computer-readable storage media (CRSM). The CRSM may includeone or more of an electronic storage medium, a magnetic storage medium,an optical storage medium, a magneto-optical storage medium, a quantumstorage medium, a mechanical computer storage medium, and so forth. TheCRSM may provide storage of computer-readable instructions describingdata structures, processes, applications, programs, other modules, orother data for the operation of the system 500. In some implementations,the CRSM may include a data store that provides storage ofcomputer-readable instructions or other information in a non-transitoryformat. The CRSM may be incorporated into the system 500 or may beexternal with respect to the system 500. The CRSM may include read-onlymemory, random access memory, or both. One or more CRSM suitable fortangibly embodying computer program instructions and data may includeany type of non-volatile memory, including but not limited to:semiconductor memory devices, such as EPROM, EEPROM, and flash memorydevices; magnetic disks such as internal hard disks and removable disks;magneto-optical disks; and CD-ROM and DVD-ROM disks. In some examples,the processor(s) 510 and the memory 520 may be supplemented by, orincorporated into, one or more application-specific integrated circuits(ASICs).

The system 500 may include one or more I/O devices 550. The I/Odevice(s) 550 may include one or more input devices such as a keyboard,a mouse, a pen, a game controller, a touch input device, an audio inputdevice (e.g., a microphone), a gestural input device, a haptic inputdevice, an image or video capture device (e.g., a camera), or otherdevices. In some examples, the I/O device(s) 550 may also include one ormore output devices such as a display, LED(s), an audio output device(e.g., a speaker), a printer, a haptic output device, and so forth. TheI/O device(s) 550 may be physically incorporated in one or morecomputing devices of the system 500, or may be external with respect toone or more computing devices of the system 500.

The system 500 may include one or more I/O interfaces 540 to enablecomponents or modules of the system 500 to control, interface with, orotherwise communicate with the I/O device(s) 550. The I/O interface(s)540 may enable information to be transferred in or out of the system500, or between components of the system 500, through serialcommunication, parallel communication, or other types of communication.For example, the I/O interface(s) 540 may comply with a version of theRS-232 standard for serial ports, or with a version of the IEEE 1284standard for parallel ports. As another example, the I/O interface(s)540 may be configured to provide a connection over Universal Serial Bus(USB) or Ethernet. In some examples, the I/O interface(s) 540 may beconfigured to provide a serial connection that is compliant with aversion of the IEEE 1394 standard.

The I/O interface(s) 540 may also include one or more network interfacesthat enable communications between computing devices in the system 500,or between the system 500 and other network-connected computing systems.The network interface(s) may include one or more network interfacecontrollers (NICs) or other types of transceiver devices configured tosend and receive communications over one or more communication networksusing any network protocol.

Computing devices of the system 500 may communicate with one another, orwith other computing devices, using one or more communication networks.Such communication networks may include public networks such as theinternet, private networks such as an institutional or personalintranet, or any combination of private and public networks. Thecommunication networks may include any type of wired or wirelessnetwork, including but not limited to local area networks (LANs), widearea networks (WANs), wireless WANs (WWANs), wireless LANs (WLANs),mobile communications networks (e.g., 3G, 4G, Edge, etc.), and so forth.In some implementations, the communications between computing devicesmay be encrypted or otherwise secured. For example, communications mayemploy one or more public or private cryptographic keys, ciphers,digital certificates, or other credentials supported by a securityprotocol, such as any version of the Secure Sockets Layer (SSL) or theTransport Layer Security (TLS) protocol.

The system 500 may include any number of computing devices of any type.The computing device(s) may include, but are not limited to: a personalcomputer, a smartphone, a tablet computer, a wearable computer, animplanted computer, a mobile gaming device, an electronic book reader,an automotive computer, a desktop computer, a laptop computer, anotebook computer, a game console, a home entertainment device, anetwork computer, a server computer, a mainframe computer, a distributedcomputing device (e.g., a cloud computing device), a microcomputer, asystem on a chip (SoC), a system in a package (SiP), and so forth.Although examples herein may describe computing device(s) as physicaldevice(s), implementations are not so limited. In some examples, acomputing device may include one or more of a virtual computingenvironment, a hypervisor, an emulation, or a virtual machine executingon one or more physical computing devices. In some examples, two or morecomputing devices may include a cluster, cloud, farm, or other groupingof multiple devices that coordinate operations to provide loadbalancing, failover support, parallel processing capabilities, sharedstorage resources, shared networking capabilities, or other aspects.

Implementations and all of the functional operations described in thisspecification may be realized in digital electronic circuitry, or incomputer software, firmware, or hardware, including the structuresdisclosed in this specification and their structural equivalents, or incombinations of one or more of them. Implementations may be realized asone or more computer program products, i.e., one or more modules ofcomputer program instructions encoded on a computer readable medium forexecution by, or to control the operation of, data processing apparatus.The computer readable medium may be a machine-readable storage device, amachine-readable storage substrate, a memory device, a composition ofmatter effecting a machine-readable propagated signal, or a combinationof one or more of them. The term “computing system” encompasses allapparatus, devices, and machines for processing data, including by wayof example a programmable processor, a computer, or multiple processorsor computers. The apparatus may include, in addition to hardware, codethat creates an execution environment for the computer program inquestion, e.g., code that constitutes processor firmware, a protocolstack, a database management system, an operating system, or acombination of one or more of them. A propagated signal is anartificially generated signal, e.g., a machine-generated electrical,optical, or electromagnetic signal that is generated to encodeinformation for transmission to suitable receiver apparatus.

A computer program (also known as a program, software, softwareapplication, script, or code) may be written in any appropriate form ofprogramming language, including compiled or interpreted languages, andit may be deployed in any appropriate form, including as a standaloneprogram or as a module, component, subroutine, or other unit suitablefor use in a computing environment. A computer program does notnecessarily correspond to a file in a file system. A program may bestored in a portion of a file that holds other programs or data (e.g.,one or more scripts stored in a markup language document), in a singlefile dedicated to the program in question, or in multiple coordinatedfiles (e.g., files that store one or more modules, sub programs, orportions of code). A computer program may be deployed to be executed onone computer or on multiple computers that are located at one site ordistributed across multiple sites and interconnected by a communicationnetwork.

The processes and logic flows described in this specification may beperformed by one or more programmable processors executing one or morecomputer programs to perform functions by operating on input data andgenerating output. The processes and logic flows may also be performedby, and apparatus may also be implemented as, special purpose logiccircuitry, e.g., an FPGA (field programmable gate array) or an ASIC(application specific integrated circuit).

Processors suitable for the execution of a computer program include, byway of example, both general and special purpose microprocessors, andany one or more processors of any appropriate kind of digital computer.Generally, a processor may receive instructions and data from a readonly memory or a random access memory or both. Elements of a computercan include a processor for performing instructions and one or morememory devices for storing instructions and data. Generally, a computermay also include, or be operatively coupled to receive data from ortransfer data to, or both, one or more mass storage devices for storingdata, e.g., magnetic, magneto optical disks, or optical disks. However,a computer need not have such devices. Moreover, a computer may beembedded in another device, e.g., a mobile telephone, a personal digitalassistant (PDA), a mobile audio player, a Global Positioning System(GPS) receiver, to name just a few. Computer readable media suitable forstoring computer program instructions and data include all forms ofnon-volatile memory, media and memory devices, including by way ofexample semiconductor memory devices, e.g., EPROM, EEPROM, and flashmemory devices; magnetic disks, e.g., internal hard disks or removabledisks; magneto optical disks; and CD ROM and DVD-ROM disks. Theprocessor and the memory may be supplemented by, or incorporated in,special purpose logic circuitry.

To provide for interaction with a user, implementations may be realizedon a computer having a display device, e.g., a CRT (cathode ray tube) orLCD (liquid crystal display) monitor, for displaying information to theuser and a keyboard and a pointing device, e.g., a mouse or a trackball,by which the user may provide input to the computer. Other kinds ofdevices may be used to provide for interaction with a user as well; forexample, feedback provided to the user may be any appropriate form ofsensory feedback, e.g., visual feedback, auditory feedback, or tactilefeedback; and input from the user may be received in any appropriateform, including acoustic, speech, or tactile input.

Implementations may be realized in a computing system that includes aback end component, e.g., as a data server, or that includes amiddleware component, e.g., an application server, or that includes afront end component, e.g., a client computer having a graphical userinterface or a web browser through which a user may interact with animplementation, or any appropriate combination of one or more such backend, middleware, or front end components. The components of the systemmay be interconnected by any appropriate form or medium of digital datacommunication, e.g., a communication network. Examples of communicationnetworks include a local area network (“LAN”) and a wide area network(“WAN”), e.g., the Internet.

The computing system may include clients and servers. A client andserver are generally remote from each other and typically interactthrough a communication network. The relationship of client and serverarises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other.

While this specification contains many specifics, these should not beconstrued as limitations on the scope of the disclosure or of what maybe claimed, but rather as descriptions of features specific toparticular implementations. Certain features that are described in thisspecification in the context of separate implementations may also beimplemented in combination in a single implementation. Conversely,various features that are described in the context of a singleimplementation may also be implemented in multiple implementationsseparately or in any suitable sub-combination. Moreover, althoughfeatures may be described above as acting in certain combinations andeven initially claimed as such, one or more features from a claimedcombination may in some examples be excised from the combination, andthe claimed combination may be directed to a sub-combination orvariation of a sub-combination.

Similarly, while operations are depicted in the drawings in a particularorder, this should not be understood as requiring that such operationsbe performed in the particular order shown or in sequential order, orthat all illustrated operations be performed, to achieve desirableresults. In certain circumstances, multitasking and parallel processingmay be advantageous. Moreover, the separation of various systemcomponents in the implementations described above should not beunderstood as requiring such separation in all implementations, and itshould be understood that the described program components and systemsmay generally be integrated together in a single software product orpackaged into multiple software products.

A number of implementations have been described. Nevertheless, it willbe understood that various modifications may be made without departingfrom the spirit and scope of the disclosure. For example, various formsof the flows shown above may be used, with steps re-ordered, added, orremoved. Accordingly, other implementations are within the scope of thefollowing claim(s).

The invention claimed is:
 1. A computer-implemented method comprising:receiving, by at least one processor, a request including at least oneimage of an object, the at least one image generated using an imagecapture device associated with a user; determining, by the at least oneprocessor, whether the request is fraudulent based on a correlationbetween damage to the object depicted in the at least one image andtelematics data obtained by one or more sensors positioned on theobject, wherein determining whether the request is fraudulent comprises:determining that the damage depicted in the at least one image is at afirst location on the object; at least one of: determining, based on thetelematics data, that a force was applied to the object at a secondlocation on the object, or determining, based on the telematics data, afailure of one or more components of the object at the second locationon the object; comparing the first location and the second location, anddetermining whether the request is fraudulent based on the comparison ofthe first location and the second location; subsequent to determiningwhether the request is fraudulent, transmitting, by the at least oneprocessor, the at least one image to a computer-implemented imageanalysis system and receiving, in response, information indicating astate of the object; and transmitting, by the at least one processor,the information indicating the state of the object for presentation on acomputing device.
 2. The computer-implemented method of claim 1, whereinthe object comprises a vehicle.
 3. The computer-implemented method ofclaim 1, wherein the one or more sensors comprise at least one of: anaccelerometer, or a fault sensor.
 4. The computer-implemented method ofclaim 1, wherein the information indicating the state of the objectcomprises an indication of damage to the object.
 5. Thecomputer-implemented method of claim 1, wherein the informationindicating the state of the object comprises a confidence levelassociated with the state of the object.
 6. A system comprising: atleast one processor; and a memory communicatively coupled to the atleast one processor, the memory storing instructions which, whenexecuted by the at least one processor, cause the at least one processorto perform operations comprising: receiving a request including at leastone image of an object, the at least one image generated using an imagecapture device associated with a user; determining whether the requestis fraudulent based on a correlation between damage to the objectdepicted in the at least one image and telematics data obtained by oneor more sensors positioned on the object, wherein determining whetherthe request is fraudulent comprises: determining that the damagedepicted in the at least one image is at a first location on the object;at least one of: determining, based on the telematics data, that a forcewas applied to the object at a second location on the object, ordetermining, based on the telematics data, a failure of one or morecomponents of the object at the second location on the object; comparingthe first location and the second location, and determining whether therequest is fraudulent based on the comparison of the first location andthe second location; subsequent to determining whether the request isfraudulent, transmitting the at least one image to acomputer-implemented image analysis system and receiving, in response,information indicating a state of the object; and transmitting theinformation indicating the state of the object for presentation on acomputing device.
 7. The system of claim 6, wherein the object comprisesa vehicle.
 8. The system of claim 6, wherein the one or more sensorscomprise at least one of: an accelerometer, or a fault sensor.
 9. Thesystem of claim 6, wherein the information indicating the state of theobject comprises an indication of damage to the object.
 10. The systemof claim 6, wherein the information indicating the state of the objectcomprises a confidence level associated with the state of the object.11. One or more non-transitory computer-readable media storinginstructions which, when executed by at least one processor, cause theat least one processor to perform operations comprising: receiving arequest including at least one image of an object, the at least oneimage generated using an image capture device associated with a user;determining whether the request is fraudulent based on a correlationbetween damage to the object depicted in the at least one image andtelematics data obtained by one or more sensors positioned on theobject, wherein determining whether the request is fraudulent comprises:determining that the damage depicted in the at least one image is at afirst location on the object; at least one of: determining, based on thetelematics data, that a force was applied to the object at a secondlocation on the object, or determining, based on the telematics data, afailure of one or more components of the object at the second locationon the object; comparing the first location and the second location, anddetermining whether the request is fraudulent based on the comparison ofthe first location and the second location; subsequent to determiningwhether the request is fraudulent, transmitting the at least one imageto a computer-implemented image analysis system and receiving, inresponse, information indicating a state of the object; and transmittingthe information indicating the state of the object for presentation on acomputing device.
 12. The one or more non-transitory computer-readablemedia of claim 11, wherein the object comprises a vehicle.
 13. The oneor more non-transitory computer-readable media of claim 11, wherein theone or more sensors comprise at least one of: an accelerometer, or afault sensor.
 14. The one or more non-transitory computer-readable mediaof claim 11, wherein the information indicating the state of the objectcomprises an indication of damage to the object.
 15. The one or morenon-transitory computer-readable media of claim 11, wherein theinformation indicating the state of the object comprises a confidencelevel associated with the state of the object.